Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle City Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Northumbrian Piper

reference
2004/007.G2
name
Northumbrian Piper
tree-preservation-order

undefined

2004/007
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-1.647875 55.020892,-1.647828 55.020709,-1.647819 55.020683,-1.647814 55.020674,-1.647786 55.020677,-1.647669 55.020682,-1.647652 55.020681,-1.647629 55.020686,-1.647619 55.020691,-1.647612 55.020697,-1.647607 55.020706,-1.647607 55.020717,-1.647694 55.020985,-1.647726 55.021110,-1.647730 55.021119,-1.647741 55.021129,-1.647764 55.021138,-1.647778 55.021140,-1.647793 55.021140,-1.647835 55.021131,-1.647861 55.021121,-1.647890 55.021103,-1.647899 55.021095,-1.647900 55.021092,-1.647906 55.021086,-1.647909 55.021071,-1.647906 55.021018,-1.647904 55.021015,-1.647904 55.021008,-1.647906 55.021003,-1.647912 55.020996,-1.647924 55.020989,-1.647939 55.020985,-1.647949 55.020984,-1.647954 55.020985,-1.648040 55.020976,-1.648053 55.020971,-1.648062 55.020965,-1.648069 55.020954,-1.648069 55.020944,-1.648066 55.020939,-1.648066 55.020932,-1.648064 55.020927,-1.648056 55.020919,-1.648042 55.020913,-1.648032 55.020911,-1.648017 55.020911,-1.647941 55.020912,-1.647932 55.020914,-1.647912 55.020913,-1.647897 55.020909,-1.647887 55.020904,-1.647878 55.020896,-1.647876 55.020891,-1.647875 55.020892)))
point
POINT (-1.647792 55.020903)
notes
These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date
2022-07-01
start-date
2004-11-04
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL